-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat/e2e-test-pipeline #15
Conversation
Signed-off-by: Frank Kloeker <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Please open an issue regarding my reviews.
We shouldn't build a latest image in the main branch, as the main branch doesn't always need to be fully functional, and directly tagging something with latest
means that it will get pulled automatically by various runtimes. The latest
image (as well as a properly versioned image) should be produced when git tags are created.
@jonathan-mayer @JTaeuber waiting on your approval here, when you got some time. @Fovty Thanks for creating the issue 👍 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Problem to solve
Creating a fully functional e2e pipeline
Proposal
Clone sparrow e2e pipeline and adapt it accordingly
Who can address the issue
Other links/references